Magnum One

home *** CD-ROM | disk | FTP | other *** search

/ Magnum One / Magnum One (Mid-American Digital) (Disc Manufacturing).iso / d20 / amax_220.arc / AMAX.DOC next >

Wrap

Text File | 1990-12-16 | 86KB | 1,667 lines

AMAX Version 2.20 An Outbound Mail Management Utility for BinkleyTerm Sysops Program and Documentation Copyright (C) 1988, 1989, 1990 Alan D. Applegate All Rights Reserved AMAX IS NOT PUBLIC DOMAIN SOFTWARE! AMAX IS COPYRIGHTED SOFTWARE. YOU ARE ENTITLED TO USE AND DISTRIBUTE THE AMAX PACKAGE ONLY IN ACCORDANCE WITH THE LICENSE AGREEMENT CONTAINED HEREIN. "AMAX" is a trademark of Alan D. Applegate AMAX Version 2.20 - Documentation - Page 2 TABLE OF CONTENTS Section 1 - Miscellaneous and Legal Stuff 3 Acknowledgements 3 License Agreement, Warranty and Statement of Liability 3 Other Uses (Non-Licensed Uses) 4 Distribution Notice 4 Archives 4 Purchasing AMAX Copies 5 Source Code 5 Section 2 - Operation 5 Introduction 5 Terminology 6 Set-Up 6 Starting AMAX 6 General Use Information 7 FIDOUSER.LST 7 Zone Support 7 Escaping 8 Compressed Mail Unpacking 8 View - View/Edit Outbound Area 9 Delete 9 Reroute 9 Flavor 10 More 11 Limit 11 Continue 11 Previous 11 Quit 11 Other Functions 11 Request - Request Files From a System 12 File Requests 12 Update Requests 12 Send - Send a File to a System 13 Enter - Enter a Message Directly to Outbound Area 14 List Send - Send a Message or File to Mailing List Mem 15 Poll - Build Attach to Poll a System 17 Undialable - Maintain Undialable Systems List 17 Display - Display Nodelist Record 18 Zone - Change Current Zone 18 Jump - Jump to DOS Temporarily 18 Alternate - Display Alternate Menu 19 Packer - Invoke Packer Designated on Command Line 19 Notes - Notes on AMAX 19 Write - Change to DOS/BIOS Screen Writes 19 Courtesy - Turn File Request Courtesy Message On/ 20 Tearline - Turn Message Entry Tearline On/Off 20 Binary - Save Settings to Binary Config File 20 Return - Return to Main Menu 20 Options - Display Options Menu 20 Sort - Change Outbound Sort 20 Mail - Turn Compressed Mail Display On/Off 21 Zero - Display Zero-Length Compressed Mail 21 Return - Return to Main Menu 21 Configuration File 21 Command Line Parameters 22 Troubleshooting 26 Solving Specific Outbound Mail Problems 27 Summary 29 AMAX Version 2.20 - Documentation - Page 3 ------------------------------------------ Section 1 - MISCELLANEOUS AND LEGAL STUFF ------------------------------------------ ACKNOWLEDGEMENTS My thanks to everyone who has tested this thing in its development process and made worthwhile suggestions to improve it, especially Charlie Frnka for pushing me along and helping code some of this beast. Thanks go out to Mark Willecke and all AMAX beta testers (past and present) who played with and generally got very excited about AMAX. Last but certainly not least, my thanks go out to everyone who has submitted suggestions for and given compliments about AMAX. The overwhelming support and wide spread usage of AMAX is very encouraging. Any trademarks that are mentioned within the software or this documentation are the property of their respective trademark owner, and no claim is made to the contrary. The mention of any particular product within this documentation should not be construed as an endorsement of or recommendation for any particular product. LICENSE AGREEMENT, WARRANTY AND STATEMENT OF LIABILITY The term "the package" refers to the AMAX software and documentation, individually and severally. The term "the author" shall be construed to mean Alan D. Applegate. The package is the exclusive property of the author, and is protected by copyright laws. By obtaining a copy of the package, you do not "own" a copy...all property rights are retained by the author. This License grants limited rights to OPERATE and to DISTRIBUTE the package in accordance with the terms listed herein. Any other use constitutes a violation of the author's rights under United States Copyright Law, and applicable international treaties. You may operate the software and/or give copies of the software distribution package to others, but only in a form that permits inclusion of all files as found in the original, archived form in which AMAX is distributed by the author. You are not permitted to modify any portion of the package in any way, including, but not limited to adding files to or removing files from the distribution package, changing or editing the documentation, and/or changing or modifying the executable program. Addition of archive "comments" is discouraged. If you find the program to be of use, you are expected and AMAX Version 2.20 - Documentation - Page 4 encouraged to forward a tax deductible donation to your local Humane Society to support their efforts. If monies are sent to the author, they will be forwarded directly to Denver Dumb Friends League, Inc., the author's local Humane Society chapter. AMAX is not provided with any warranty of any kind, including, but not limited to fitness for any particular purpose. IMPORTANT NOTE: If this License or any portion thereof is not legally valid in your geographical area or jurisdiction, THIS LICENSE IS WITHDRAWN and YOU ARE NOT LICENSED TO USE OR DISTRIBUTE THE PACKAGE! WARNING! YOU USE AMAX ENTIRELY AT YOUR OWN RISK! The author will NOT be responsible for any loss of data, loss of business, loss of monies or any other damages resulting from the use of, or inability to use AMAX. By operating the program, you accept and acknowledge responsibility IN FULL for all occurrences related to your use of the program. In any jurisdiction where such limitation of liability is restricted or forbidden, this program IS NOT licensed for legal use. This warning is also given on program start-up. OTHER USES (NON-LICENSED USES) Use and distribution outside the scope of the License Agreement above is strictly prohibited, unless prior, written permission is obtained from the author. Inquiries may be directed to: AMAX License, c/o Alan D. Applegate, P. O. Box 260723, Lakewood, CO, 80226-0723, USA. Include a self-addressed, stamped envelope for replies. DISTRIBUTION NOTICE This package may be posted for download or file request by any FidoNet system in archived form, and in adherence to the terms of the License above. No profit may be realized directly from such distribution, although AMAX may be provided for download on "pay systems" if desired. ARCHIVES The regular distribution version of AMAX is archived using LHARC by Haruyasu Yoshizaki. This program offers excellent compression characteristics, without the political ramifications inherent in using other archiving software. If you feel it necessary to re-archive AMAX in a format other than the format it's delivered in, go ahead, but you should read the License Agreement carefully. Any distribution of AMAX requires that ALL the files AS ORIGINALLY DISTRIBUTED must be included. Make certain that you have a full, original version, and make sure all the files in the package find their way into your new archive. Addition of files to the distribution is AMAX Version 2.20 - Documentation - Page 5 prohibited. The author frowns on the addition of archive "comments" to any AMAX archive. PURCHASING AMAX COPIES AMAX is also available on diskette with printed documentation in an attractive binder for $20.00, within the USA, $40.00 outside the USA. Payment may be made by personal check if in USA; outside USA, payment must be made in US dollars, with a draft or money order drawn on a US bank. Cash may be sent AT YOUR OWN RISK if desired, but we discourage it. Send orders to: AMAX, c/o Alan D. Applegate, P. O. Box 260723, Lakewood, CO, 80226-0723, USA. This is NOT software "registration" at all - you are paying for the production, preparation and delivery of the materials. Registration of this package is not required - please make a donation to your local Humane Society instead. SOURCE CODE Source code to AMAX is not available. Please do not ask. --------------------- Section 2 - OPERATION --------------------- INTRODUCTION AMAX is a utility designed for FidoNet Sysops who use the BinkleyTerm FidoNet-compatible mail interface. Although many of AMAX's functions can be used with Opus, such operation is no longer specifically supported or recommended. AMAX provides file request generation, file attach building or appending, maintenance of undialables, outbound mail area viewing and editing, generation of poll files, on-the-fly message entry direct to the outbound mail area, mailing list functionality for both messages and files, multi-zone compatibility, nodelist look- ups with editing, editing of existing file attaches, and much more. AMAX can be used at the console with high performance direct screen writes and cursor key functionality, or may be used remotely with redirected I/O using standard ANSI X3.64 cursor control sequences. I feel strongly that you will not find a better combination of features and ease of use in other mail maintenance package. AMAX is designed to be easy to use and convenient. A compiled, ready-to-use nodelist is recommended, BUT IS OPTIONAL. Supported types are: Nodelist Type Index Name Data Name -------------------- ------------ ------------ Opus Version 5 * NODELIST.IDX NODELIST.SYS Opus Version 6 NODELIST.IDX NODELIST.DAT QuickBBS 2.0x QNL_IDX.BBS QNL_DAT.BBS AMAX Version 2.20 - Documentation - Page 6 If you do not have one of these formats available, AMAX will still be completely functional, but some cosmetic niceties will not be accessible. * Days are numbered for the Opus Version 5 (a/k/a Fido) nodelist format. In other words, the format is OBSOLETE. When the 1.1x release of Opus is finally made, there will be no current software that actively supports this format and that AMAX is compatible with. For that reason, future versions of AMAX will not support this nodelist format. It is HIGHLY recommended that all BinkleyTerm systems be using the Opus Version 6 format NOW, as it makes additional features available to the system. This benefits your BinkleyTerm installation much more than it benefits AMAX. It is also strongly recommended that you have available a FIDOUSER.LST file available for AMAX. Although not required, it strongly enhances the functionality of AMAX. If you do not have one, or are unfamiliar with them, consult your nodelist processing software for information on creating one during your weekly nodelist processing routine. TERMINOLOGY PLEASE NOTE!!! There is terminology used within this documentation that you may not be familiar with. Refer to the documentation that accompanies BinkleyTerm for more information on how mail is handled and which terms are used (the BinkleyTerm documentation contains a fairly complete glossary of terms). SET-UP AMAX uses the BINKLEY.CFG configuration file to provide the needed information. If AMAX is not run from the directory which contains the configuration file, the BINKLEY environment variable will need to be set in accordance with the BinkleyTerm documentation. If you use a configuration file other than BINKLEY.CFG, you may designate the name of that file on the command line. In the BinkleyTerm environment, AMAX works well in conjunction with user-defined DOS shell keys, as well as user-defined batch file exit keys. NOTE: Memory availability may be a problem when using DOS shell keys. STARTING AMAX Simply enter "AMAX" at the DOS prompt to start the program. After an initialization sequence, the Main Functions menu will appear. Although a large number of command line options are available to you, AMAX is designed with default settings that should be correct for most installations "off the shelf." Refer to the section "Command Line Parameters" for more information. AMAX Version 2.20 - Documentation - Page 7 GENERAL USE INFORMATION FIDOUSER.LST If you have a sorted FIDOUSER.LST, as produced by your nodelist processing software, AMAX is capable of using the list. When prompted for a node address, simply enter a Sysop name, in the form <first_name> <last_name> and AMAX will perform a look-up to find the node address. For example, if you wish to reach 104/36, you may enter "Alan Applegate" when prompted for a node address, and AMAX will search for and find the node address for Alan Applegate as shown in FIDOUSER.LST. Note that FIDOUSER.LST must be located in the current directory, or in the directory pointed to by the 'Nodelist' statement in your BinkleyTerm configuration file. (The latter is considered proper, and is required for BinkleyTerm.) Zone Support AMAX does support multiple zone operations. This is compatible with the method that BinkleyTerm uses, having a separate outbound directory for each zone. Refer to the BinkleyTerm documentation for information on setting-up these outbound directories. (If you use them without defining them first, AMAX will create them.) AMAX works on the concept of "current zone." Think of this like a DOS "current directory." All operations take place in the outbound area for the current zone until the zone is changed. The zone can be changed in one of two ways. First, you can change the zone from the Main Functions menu using the proper command. Second, you can enter a zone parameter as part of any node address entry. For example, if the current zone is zone 1, you can change to zone 2 by entering a full zone address when prompted for a node address anywhere within AMAX, like 2:510/0 for instance. If you were entering a file request for the zone 2 node, in this example the current zone and outbound directory would be changed to zone 2, and the file request would be placed there. The current zone would remain zone 2 until it is again changed. (The only exception is when rerouting files between zones. AMAX will return to the calling zone when the reroute is finished or aborted.) Note also that AMAX features zone-smart nodelist look-ups. This means that your compiled nodelist MUST contain "zone identifiers." If you use the ParseLst nodelist processor, this means that the 'UseZone' statement would be used in your PARSELST.CFG file. Note that it is possible to have nodes in other zones included your compiled nodelist, without having zone identifiers present. It's also possible to have zone identifiers present without having any nodes in other zones in your compiled nodelist. Read the documentation for your nodelist processor thoroughly if you experience a situation where AMAX cannot find a valid node in your nodelist files. AMAX Version 2.20 - Documentation - Page 8 If you cannot manage to coax AMAX into running with your nodelist, it is still quite functional without one. Refer to the section "Command Line Parameters" for more information. Escaping In most places, AMAX will accept the use of the ESCAPE ('Esc') key as input. When this key is used (and accepted by AMAX) it will ABORT the current operation WITHOUT VERIFICATION. When operations are aborted, either by pressing the ESCAPE key or by using a menu option such as Q)uit or A)bort, NO verification is requested. Please make sure you wish to abort the operation prior to pressing one of these keys, and avoid pressing them by mistake. Compressed Mail Unpacking AMAX is capable of unpacking compressed mail that has been archived with ARC (or compatible), ZOO, PKZIP or LHARC. In order for this functionality to work properly, certain unpacking utilities MUST BE ON THE DOS PATH. Note that having these programs in the AMAX directory IS NOT SUFFICIENT. COMPRESSED MAIL UNPACKING >> ONLY << WORKS IF THESE UNPACKERS ARE ON THE DOS PATH! If you need help setting the DOS path, consult your DOS manual. Note that PAKmail is not supported at this time. For ARCmail unpacking to work, Vern Buerg's ARCE program (by default) MUST be used. PKXARC, PKUNPAK and PAK (in .ARC compatibility mode) are supported, but are NOT used unless you specify them on the command line. See the "Command Line Parameters" section for information. The ARCE program MUST be named ARCE.COM or ARCE.EXE. If your copy is named something else (it may include a version number for example), you MUST rename it. NOTE: ARCE substitutes that do shelling operations to other archivers SHOULD work with AMAX, assuming adequate memory is available for the three-layer shelling that would occur as a result; such operation is NOT guaranteed, however. For ZOOmail unpacking to work, Rahul Dhesi's ZOO program MUST be used. Other .ZOO compatible unpackers ARE NOT supported. For ZIPmail unpacking to work, PKWARE's PKUNZIP program MUST be used. Other .ZIP compatible unpackers ARE NOT supported. For LZHmail unpacking to work, Haruyasu Yoshizaki's LHARC program MUST be used. Other .LZH compatible unpackers ARE NOT supported. Note that sufficient memory must exist for AMAX to shell to DOS (loading another copy of COMMAND.COM) and for the unpacker to load. This means, for example, that a total of up to 70k of memory must be available over and above AMAX's requirements for ZOOmail unpacking to work, and up to 35k for ARCmail to work. Memory requirements for other unpackers may vary. Memory AMAX Version 2.20 - Documentation - Page 9 requirements for COMMAND.COM vary for each version of DOS. Compressed mail unpacking is covered in the next section. VIEW - VIEW/EDIT OUTBOUND AREA AMAX provides outbound mail area checking and editing capabilities. AMAX is capable of displaying packets; attaches; file or update requests; call progress files; "Bad WaZOO" files; ARCmail, ZOOmail, ZIPmail and LZHmail compressed mail packets; an update request log (if one exists); and "stray" packets. Packets and attaches that are marked as "no-send" (by oMMM's LEAVE command, for example) are also displayed properly. Zero-length compressed mail packets are not displayed unless you instruct AMAX to do so (on the command line or from the appropriate menu). Editing functionality includes flavor change, deletion, and rerouting, and applies to most outbound file types. You can also opt to display complete file information for any entry (additional editing capabilities may be available when displaying information about an entry). Entries are listed to the screen 16 items per page. You can move back and forth through the listing with the Previous and Continue menu options. Please note that the ENTER key can also be used to page forward. The current page number is shown at the top of the screen along with a total page count. When keyboard BIOS calls are enabled, you may use the PgDn and PgUp keys to page through the outbound area. When you select any function from the menu, you may also use the arrow keys to choose the desired entry from those listed in lieu of entering a number. These functions are NOT available unless keyboard BIOS calls are enabled on the command line. Refer to the section "Command Line Parameters" for more information. Entries in the outbound area can be sorted by one of three factors: address, type or flavor. The default sort is by node address. You can set the sort mode with the proper command line option (see "Command Line Parameters") or with a command from the appropriate menu. Delete The Delete function will delete any file in the outbound area. You are prompted to verify your choice prior to deletion. When deleting an attach file, you will be prompted whether or not to delete or truncate the file(s) listed in the attach, if the file(s) are marked to be deleted or truncated after sending. Reroute The Reroute function allows you to readdress an entry to another node. If an equivalent entry already exists for the new destination you select, the entry will be appended to the AMAX Version 2.20 - Documentation - Page 10 existing entry. Please note that once an entry is appended to an existing entry, it cannot be "un-appended." For this reason, make certain that you make the correct choices as you go along, and double-check them. If an equivalent entry for the new destination does not exist, the entry you select will simply be renamed to reflect the new address. NOTE! The reroute function is better thought of as "redirection." To understand the difference, let's use an example. Assume you write a letter to your sister. Her name and address are both printed on the letter. You put the letter in an envelope, and address it to her. You then later decide to "redirect" the letter to your uncle (since your sister is visiting your uncle or something). You cross out her address, and write in that of your uncle. The post office will deliver it to your uncle, even though the letter inside lists your sister's address. AMAX works on a VERY similar principal. When you reroute (redirect) a packet (message), all you're doing is changing the address on the "outside." Inside, within the structure of the packet, the message is still addressed to the same person it was when you originally wrote it. BinkleyTerm will send the message to the "outside" address. AMAX is not capable of changing the "inside" address. In most cases, the recipient of the message will unpack it (take it out of the envelope) and readdress it to its original address, and send the message along. This is fine when the person you send it to is a net coordinator, but if rerouted to someone else it may cause undesired extra work and expense for that new addressee. In our previous example, this would be like your uncle sticking the letter to your sister in a new envelope, addressing it to her as the letter outlined, and he has to pay postage. This may or may not always be desired operation. Be careful and considerate when rerouting mail. Finally, when you reroute a file attach, the file WILL NOT be sent on to the destination you have when the attach was created - the file(s) will be sent to the new address and will stop there. You must use special utilities designed for file routing, which in turn requires special arrangements with any intermediary systems. Flavor The Flavor function allows you to change the routing flavor of an entry. Options are Continuous, Normal, Direct and Hold. Refer AMAX Version 2.20 - Documentation - Page 11 to your mail system documentation for information. If a file of the same type and flavor exists for the system, the file you're changing will be appended to the existing like file. More The More function displays additional information about an entry, including its date, time and size. In the case of attach files, request files and certain other raw text files, a list of the contents will be given. In the case of call progress files, the progress data will be displayed. The More function is also a "gateway" to some additional functions, outlined below in the "Other Functions" sub-section. Limit The Limit function allows you to limit (suppress) the display of certain types of files. When this function is selected, you are presented with a list of file types. Any type shown with an asterisk (*) will be limited, i.e., display of that file type will be suppressed. Simply select the proper menu entry to toggle the limiting on and off. When limits are selected as desired, press ENTER to view the outbound area. Continue The Continue function advances the display to the next page, if any. Previous The Previous function goes back to the previous display page, if any. Quit The Quit function returns you to the Main Menu. Other Functions The More function is a gateway to other AMAX functions. For compressed mail, the More Info function will allow you to unpack a compressed mail file into a single Normal packet if you so desire. Please refer to the section "General Use Information" sub-heading "Compressed Mail Unpacking" for information. Unpacking compressed mail allows you to use AMAX's PacketView (TM) function to read the messages inside. When the More function is used on packets, you may optionally view the packets themselves using the AMAX PacketView (TM) function. Simply select 'Y' for "yes" (or simply press Enter) when prompted whether to invoke PacketView. The PacketView functionality identifies the product that was used to build the packet, if known. For each message inside the packet, AMAX Version 2.20 - Documentation - Page 12 information is given about the message. Who it is to, from, and when it was entered. Some message flags may also be displayed, such as private, file attached, etc. A message counter is also provided. REQUEST - REQUEST FILES FROM A SYSTEM File Requests AMAX provides file request generation capability. When this function is invoked, you are prompted for the destination address for the request. After selecting the destination, AMAX will determine if a file request is pending for the system you're requesting from. If there is one pending, you will be prompted whether to display the contents of the existing request first. Select 'Y' for yes, 'N' or ENTER for no as appropriate. AMAX will count the number of entries in an existing file request, if any, and will display the total requests (0 if no requests are pending). You are then prompted for the name of the file desired. You may abort the process at this point be pressing ENTER or ESCAPE. Enter the name of the file, and press ENTER. You are then prompted for a password, if desired. If no password is desired, simply press ENTER. The file request counter will be incremented, and you will again be prompted for a desired file name. Continue this process as long as needed, and press ENTER alone or ESCAPE in the file name field to return to the address entry prompt. Press ENTER or ESCAPE again to return to the Main Menu. NOTE! When requesting a file, DO NOT include a drive or path designation -- just the filename alone. Otherwise an update request will be assumed. See "Update Requests" for information. NOTE! BinkleyTerm, beginning with Version 2.40, will NOT send a request without some other reason to dial the phone. If you have "courtesy messages" turned on, then a Continuous flavor packet will already have been created for you. If you have them turned off, you will need to generate a poll (using the AMAX poll function) or manually poll using BinkleyTerm in order for the request to be sent. Update Requests AMAX supports the construction of update requests for BinkleyTerm. Update requests are built using the regular file request functionality described in the previous section. To create an update request, simply enter the filename when prompted, but AMAX Version 2.20 - Documentation - Page 13 include a complete drive AND path designation, such as: C:\OPUS\MYPROG.ARC An update request will be built for the designated file. Update requests are explained in the documentation for the BinkleyTerm software. Again, a normal file request is built unless BOTH drive AND path are designated when prompted for a file name. Both file and update requests are kept inside .REQ files, which are listed as file requests when you perform a View/Edit Outbound operation. Lines inside the .REQ file that are update requests simply have a date/time stamp in addition to the file name. SEND - SEND A FILE TO A SYSTEM Attach files are used by BinkleyTerm in the process of sending files, or "file attaches," to a given system. When you enter a message and specify that a file be attached, the packer (normally oMMM) will build this attach file. The file contains information about the file(s) to send. This AMAX option allows you to build or append attach files, enabling you to send a file to a given system "on the fly" without entering a corresponding message. When this function is invoked, you are prompted for the destination node address. You are then prompted for the name of the file to send, and are then prompted to select the routing flavor to be used. Note that the file must exist when using this option...AMAX will look for the file as entered. If it does not exist, AMAX will not allow you to build the attach. Note that the name of the file MUST be entered with a complete path. Example: C:\OPUS\FILES\MYPROG.ARC When global identifiers are used, such as C:\OPUS\SYSTEM*.BBS or E:\*.ARC, AMAX will "expand" the entries when they are saved. AMAX will attempt to locate all files that correspond to the filespec given, and store each file on a separate line in the completed attach. You will be prompted as to whether the file should be truncated to zero length after sending. THIS OPTION IS OFFERED FOR MAXIMUM FUNCTIONALITY - USE IT CAUTIOUSLY! Once a file is truncated to zero length, it cannot be recovered, even by programs such as Norton, Mace or PC Tools. Normally the truncate option is used ONLY when sending compressed mail. If you choose not to have the file truncated, you will be AMAX Version 2.20 - Documentation - Page 14 prompted to choose whether it should be deleted after sending. If this option is chosen, the named file will be deleted after it is sent to the destination. Use this option carefully. Use the View/Edit Outbound Area function to check the attach file, if desired. When an existing attach file is appended, you may also wish to change the routing flavor with this option. ENTER - ENTER A MESSAGE DIRECTLY TO OUTBOUND AREA The purpose of this option is to allow you to enter a message "on the fly" DIRECTLY to the outbound area. In other words, your message will be entered and placed in the outbound holding area, the same as it would be if you entered the message with a conventional editor and afterward invoked your mail packer. You are limited to twenty (20) lines in the message. This editor is certainly not intended to replace the one you normally use. The main idea behind the Message Enter function is to allow a method of sending a quick message without calling up your full editor and then packing your message, a process that can sometimes be time consuming. When this function is selected, you are prompted for the name of the person to send the message TO. If all you know is a node address and not a name, you may enter "Sysop" as the name, then after you enter the node address, a name look-up will be performed. This look-up occurs only if you have a FIDOUSER.LST available. NOTE! This is a linear text search, and may be quite time consuming depending on your hardware configuration. Next, you may enter the name of the person the message is to be FROM. This field is "pre-filled" with the Sysop name, as given in the BinkleyTerm configuration file. Next, you may select the address of the destination system. If a FIDOUSER.LST file is available, this field will be "pre-filled" with the address found for the person named in the "To:" field, if any was found. You are then prompted as to whether the message should be marked private. Press 'P' once for a private message (indicated by "P)RIVATE"); press 'P' again to make the message non-private (indicated by "P)rivate"). Next, you will select if you would like to attach a file with the message (send a file at the same time). This is selected in the same manner as the private message select. Finally, you are prompted for the subject of the message (if no file attach) or the file name (if a file is attached). When you're ready to enter the message text, press 'E' or the ENTER key. AMAX Version 2.20 - Documentation - Page 15 Next, you are prompted whether to use a text file for the message text. You have the choice of using AMAX's built-in message editor, a text file, or a combination of both. When you wish to use the built-in editor only, simply specify not to use a text file by pressing 'N' when prompted. If you wish to use both, keep in mind that the text entered with the built-in message editor will be first in the message, and will be immediately followed by the contents of the text file you specify. Press 'Y' when prompted whether to use the text file, then enter the message. If you wish to use only the contents of the text file, then simply bypass the built-in message editor by pressing 'Y' when prompted, the press ENTER at the line 00 message editor prompt. If you will be using the built-in message editor, enter the text of the message. The twenty lines are numbered from 00 to 19. Word wrap occurs when a space is detected within 10 spaces from the end of the line. If you end a line with a very long word, you may reach the end of the line, indicated by a "beep." Backspace to erase the word, then place it on the next line. Press ENTER twice to end the message and bring-up the edit menu at the bottom of the screen. You may Edit, Save, Abort, Insert, Delete or Continue. To Edit, enter the line number of the line to edit. Enter the section of the line to change, then enter the replacement for a given section. Once editing is completed, the cursor is returned to the next available line. To Save, select the routing flavor desired - Continuous, Normal, Direct or Hold, or you may abort the process. Your message will be saved directly to the outbound holding area. To Abort, simply make the selection. To Insert, make the selection, and enter a line number for the insertion as directed. All subsequent lines, if any, will be moved down. Any lines beyond the limit of 20 will be deleted. To Delete, make the selection, and enter the line number to delete. Any lines below the delete line will be moved upward. To Continue, make the selection, and the cursor will be returned to the next available line. LIST SEND - SEND MESSAGE OR FILE TO MAILING LIST MEMBERS This function allows you to send a message or file to a list of nodes. The mailing list itself is in the same general format as the PLEASE.ALL file used by Joe DeRosa's Please program. Here is a sample PLEASE.ALL file: AMAX Version 2.20 - Documentation - Page 16 ; PLEASE.ALL file for 1:104/36 ; "MyNodes" is the list of nodes I hub for MYNODES 104/608 104/904 104/19 104/58 104/60 104/311 104/312 104/604 104/314 104/555 104/41 104/315 1052/6 . ; "Hubs" lets me send to all the AdminHubs HUBS 104/100 104/200 104/400 104/500 104/600 104/700 . ; "Test" was used with AMAX testing TEST2 104/608 104/904 132/101 141/491 160/50 104/500 104/311 TEST2 104/312 104/314 JOE_BLOW 104/610 104/19 104/40 1052/5 TEST2 1052/6 CHARLIE_FRNKA 132/101 MARK_WILLECKE 104/801 TEST2 104/700 DANIEL_SEGARD . ; "Short" is another test list SHORT 104/904 132/101 141/491 . Since the format specifications were not explicitly given in the Please program documentation, some guidelines were created for this file as it applies to AMAX. These guidelines may or MAY NOT be compatible with Please. They are: - Comments MUST be indicated with a semi-colon (;) - Comments MUST be one continuous line (not wrapped) - Keywords are NOT case sensitive - Wrapped lines for a given list MAY or MAY NOT be started with a repeat of the keyword (your choice) - All lists MUST be terminated with a single period (.) regardless of whether each line begins with a keyword - Each line of text MUST terminate with a standard carriage return/linefeed sequence; other terminations not allowed - If zones are used, they MUST be used on ALL entries - Sysop names may be used in the list, but first and last names MUST be separated with an underscore (_) and MUST be able to be located in FIDOUSER.LST (which means that FIDOUSER.LST must be available) Though the file takes the same general format as the PLEASE.ALL file, the filename is NOT hard coded into AMAX...any filename may be designated. When the List Send function is invoked, you are prompted for the name of the list send file (PLEASE.ALL is the default). Enter the filename (or press ENTER to accept PLEASE.ALL), preceded by a drive and path designation if desired. Next, you are prompted for the keyword that identifies the list you wish to send to. In the example above, if I entered the keyword "SHORT" AMAX would send to 104/904, 132/101 and 141/491. Next, you are prompted whether to send a message or file. Pick as appropriate. To send a message, follow the directions as given for the Message Enter function. To send a file, simply designate the name of the file, including a complete drive and path specification. Globals may also be used in the filename, and will be expanded as the attach files are created. AMAX Version 2.20 - Documentation - Page 17 The routing flavor you select when saving the message or file will be used for ALL the destination nodes listed with the selected keyword. You may wish to select Normal, then invoke your mail packer afterward to ensure that the message or file is correctly processed. The list send functionality can also support zones. It works in the same manner as zone support works elsewhere in AMAX, with the concept of current zone. NOTE! When you choose to use zones within the mailing list file (such as PLEASE.ALL), you MUST use them on ALL node addresses in the file - not just selected entries! Such as this example: ; Sample Fully Zoned PLEASE.ALL File MY_LIST 2:501/0 2:490/16 1:104/610 3:635/800 2:334/2 MY_LIST 1:3001/1 3:632/301 2:30/11 . ; Local Group LOCAL 1:104/904 1:104/312 1:104/604 1:104/400 . NOTE! If you do not precede EACH entry with a zone, operation of AMAX will be VERY UNPREDICTABLE! NOTE! The Please program, beginning with Version 2.10, supports zones. I have not determined whether it supports them in the same manner and format that AMAX does within the PLEASE.ALL file. I assume that the way AMAX supports them in PLEASE.ALL is compatible, but you will need to determine on your own whether specifying zones will break your copy of Please (if you use it) before continuing. POLL - BUILD ATTACH TO POLL A SYSTEM This function allows you to build a null .CLO file (continuous file attach) that should force your system to initiate a call to the system you're polling. Of course, this depends entirely on whether or not your current system event allows for Continuous mail to be sent to the desired system. The purpose for this feature is simply to offer an alternative to initiating a manual poll. It will not replace a manual poll in all situations, however, as a manual poll will override any valid, current event settings. UNDIALABLE - MAINTAIN UNDIALABLE SYSTEMS LIST Call progress entries are used by BinkleyTerm to keep track of how many call attempts have been made to a specific destination system, and how many unsuccessful connects have been made. Refer to the BinkleyTerm documentation for more information. Selecting this option allows you to delete call progress files, as well as create them to "force" BinkleyTerm to stop dialing a particular system. AMAX Version 2.20 - Documentation - Page 18 When a user-defined limit of unsuccessful connects has been made, the system will no longer attempt to call the given destination. Clearing the entry allows the system to once again attempt connection. The default BinkleyTerm settings is three calls. When you select this option, you will be asked whether you want to clear undialables, or add undialables. If you wish to clear them, then call progress entries, if any, will be displayed with the system node address, name and location. You are prompted whether to delete the particular entry. If you wish to add entries, you are prompted for the desired node address. When entered, an undialable record will be added to the outbound area for that system, showing 0 call attempts, and 3 bad connects. This option will only work for systems set to stop dialing after 3 (BinkleyTerm default) or fewer bad connects. If your system is set higher, using this function will NOT stop BinkleyTerm from making a call. DISPLAY - DISPLAY NODELIST RECORD This function allows you to display the complete record for a given node as found in the compiled nodelist files your system is using. Simply enter a node address (or Sysop name if FIDOUSER.LST is available) and press ENTER. If a nodelist record is found, it will be displayed. If none is found, a blank space will be displayed. This function is not valid if no nodelist is being used. If FIDOUSER.LST is available, and if you entered a node address for this function (not a Sysop name), then an automatic Sysop name look-up will occur. This is a linear search, and may be somewhat time consuming. This function will also allow you do edit certain fields in the nodelist record if you're using an Opus Version 6 nodelist type. ZONE - CHANGE CURRENT ZONE This allows you to change AMAX's current zone. This concept is explained in the section "General Use Information," sub-heading "Zone Support." JUMP - JUMP TO DOS TEMPORARILY Allows you to execute what is commonly referred to as a "DOS Shell." Simply invoke this option, and AMAX will load another copy the DOS command processor, and a DOS prompt will be displayed. You can perform most all normal DOS operations in the shell, including running other programs. AMAX locates COMMAND.COM based on the COMSPEC environment variable. AMAX Version 2.20 - Documentation - Page 19 Keep in mind that AMAX stays in memory during the shell, and will limit the amount of space you have for other operations. This command is not recommended in multi-tasking environments. If the command fails, it is almost certainly because there is not sufficient memory to load another copy of DOS. Type "EXIT" at the DOS prompt to return to AMAX, as directed by the special DOS prompt displayed while in the shell. ALTERNATE - DISPLAY ALTERNATE MENU When the Main Menu is active, this option changes the display to the Alternate Menu, which offers a few more AMAX functions. The Alternate Menu is intended to provide additional functions that space would not permit to be on the Main Menu. PACKER - INVOKE PACKER DESIGNATED ON COMMAND LINE This function will only be visible if you have designated a packer on the AMAX command line. This function allows you to run your packing program from AMAX. The name of the program is designated on the AMAX command line (see "Command Line Parameters"). Since you cannot pass command line parameters to the packer, you should create a batch file that invokes your packer with the proper command line, and call the batch file from AMAX. The purpose of this command is to allow you to make changes or additions with AMAX, then invoke the packer to ensure that any new or changed entries are correctly processed for sending. NOTES - NOTES ON AMAX This option causes AMAX to display a short information panel about the program, and details about a special offer for AMAX users. WRITE - CHANGE TO DOS/BIOS SCREEN WRITES !!! DANGER !!! This option will toggles between DOS and BIOS screen writes. Direct (BIOS) screen writes increase AMAX performance. DIRECT SCREEN WRITES WILL CAUSE AMAX NOT TO WORK WHEN USED REMOTELY! IF USING AMAX REMOTELY, DO NOT USE THIS OPTION! DANGER!!! DIRECT SCREEN WRITES SHOULD BE USED ONLY ON SYSTEMS THAT ARE 100% IBM-PC HARDWARE COMPATIBLE! DANGER!!! Systems such as the DEC Rainbow DO NOT support direct screen writes as implemented with AMAX! Using this option to turn on direct screen writes on a system that AMAX Version 2.20 - Documentation - Page 20 doesn't support it may cause a hardware lock-up! COURTESY - TURN FILE REQUEST COURTESY MESSAGE ON/OFF When this setting is on, a message packet will be constructed whenever a file request is generated using AMAX. This will alert and thank the Sysop of the destination system that a file request has been made, and is considered a "courteous touch." If a raw text file named AMAXFREQ.TXT exists in the current directory, this text will be used for the body of the courtesy message. Otherwise, a default line of text used. TEARLINE - TURN MESSAGE ENTRY TEARLINE ON/OFF This allows you to toggle on and off whether a tearline and origin line will be added to the end of messages you enter using AMAX. If this option is on, an AMAX tearline and your origin line will be used, and look like this: * Origin: My System (1:999/100) --- AMAX 2.20 Otherwise, no tearline or origin line are used. The current status of this option is shown on the Alternate Functions menu. BINARY - SAVE SETTINGS TO BINARY CONFIG FILE Selecting this option causes AMAX to store all current command line settings (except the -g option) to a binary configuration file named AMAX.CFG. If this file exists, AMAX will use the settings in the file (even if no command line parameters are used) when you start the program. That means that you can configure your settings with command line switches once, then use AMAX without command line switches thereafter. RETURN - RETURN TO MAIN MENU This option returns you to the AMAX Main Menu. OPTIONS - DISPLAY OPTIONS MENU When the Main Menu is active, this option changes the display to the Options Menu, which offers a few more AMAX functions. The Option Menu is intended to provide additional functions that pertain to viewing and editing the outbound area. SORT - CHANGE OUTBOUND SORT The Alternate Functions menu shows the current default sort mode, and what mode will be selected by choosing this AMAX Version 2.20 - Documentation - Page 21 option. Using this option causes AMAX to cycle the default sort mode through the various selections. The sort mode is used when the View/Edit Outbound Area function is invoked, and determines what (if any) sort will be performed on the information to be displayed. MAIL - TURN COMPRESSED MAIL DISPLAY ON/OFF This option toggles whether compressed mail will be displayed. With this option on, compressed mail files will be listed when doing an outbound view/edit. ZERO - DISPLAY ZERO-LENGTH COMPRESSED MAIL This option toggles whether zero-length (truncated) compressed mail will displayed during an outbound view/edit. Note that compressed mail display must be toggled on in order for this function to have any effect. RETURN - RETURN TO MAIN MENU This function will return you to the Main Menu. CONFIGURATION FILE Since AMAX is designed for use with BinkleyTerm, by default it uses BinkleyTerm's configuration file BINKLEY.CFG. If special situations exist, then a separate configuration file can be created just for AMAX. There are six items that AMAX requires to be in the file. Use any standard text editor or DOS's own EDLIN program to create the file, and put only one item per line. HOLD Example: HOLD c:\binkley\outbound\ This tells AMAX where your outbound mail area is located. Designate a drive and complete path. NODELIST Example: NODELIST c:\binkley\ This tells AMAX where your nodelist is located. Designate a drive and complete path. DO NOT designate the filename. SYSOP Example: SYSOP Joe Blow This simply gives your name. AMAX will use it on the "from" line during message entry. ADDRESS Example: ADDRESS 1:104/36.1 This is your full node address. This statement was new with BinkleyTerm 2.10, and should be used as a replacement for AMAX Version 2.20 - Documentation - Page 22 POINT, BOSS and ZONE. See the BinkleyTerm documentation for information. POINTNET Example: POINTNET 1052 For use in point installations, this statement designates the net address assigned to you by your boss, also known as a "fake" address. DO NOT put the node number in, JUST the net number. If you are 1:104/36.2, and your fake address is 1052/2, then place 1:104/36.2 with the ADDRESS statement and 1052 with the POINTNET statement. See the BinkleyTerm docs for details. DO NOT use this statement if you also use the BOSS and/or POINT statements. SYSTEM Example: SYSTEM This Is My System Name This designates the name of your system. In AMAX, it is used to create an origin line for use when using the quick message entry function. PLEASE NOTE! AMAX supports the following statements FOR BACKWARDS COMPATIBILITY ONLY: Zone Point Boss IMPORTANT! THESE STATEMENTS ARE OBSOLETE FOR BOTH BINKLEYTERM AND AMAX. Addressing should ALWAYS be specified with an 'Address' statement when using BinkleyTerm 2.10 or higher! A sample configuration file with the information needed by AMAX might look like the following: HOLD c:\binkley\outbound\ NODELIST c:\binkley\nodelist\ ADDRESS 1:104/900.0 SYSOP Joe Blow SYSTEM My System Name COMMAND LINE PARAMETERS There are several command line parameters available for use with AMAX. Command line parameters can be used in any combination, in any order, or not at all if so desired. Most command line options can also be set or changed from one of the AMAX menus. -? Displays brief listing of command line parameters. -a The -a option causes compressed mail to NOT be displayed AMAX Version 2.20 - Documentation - Page 23 when the View/Edit Outbound function is used. Your selection can be changed with an option from the appropriate menu. -b The -b option tells AMAX to bypass the user warning screen normally displayed on start-up. Once you have read and understand the warning screen, this option may be used. -c The -c option explicitly designates the path and filename of a configuration file. This option is used in multi-tasking environments, with Opus-CBCS, or whenever you wish not to use the default configuration file BINKLEY.CFG. Example: amax -cc:\opus\amax.cfg The example would specify that AMAX use a configuration file named AMAX.CFG located on C: drive in the OPUS sub- directory. Of course, the configuration file specified must follow the format outlined in the section "Configuration File." -d The -d option tells AMAX to use direct hardware screen writes. WARNING! Direct hardware screen writes may not work with hardware that is not 100% IBM hardware compatible. -e The -e option tells AMAX to enable functions that use BIOS calls for keyboard input. This is to allow you to use the arrow keys and PgUp/PgDn in the View/Edit Outbound function. NOTE! If this option is used, AMAX will NOT be compatible with redirected I/O, and CANNOT be used remotely! -g The -g option allows you to designate command groupings to perform unattended processing of some AMAX tasks. Essentially you designate a group of commands that would be executed just as though you were at the keyboard. This allows you - with some getting used to - to replace the functionality of programs like Please, Send and Get. To make use of this function, you need to understand the task you want to perform, and step through it manually, recording the series of keypresses necessary to perform the given activity. In the -g command grouping, an equal sign AMAX Version 2.20 - Documentation - Page 24 (=) translates to a carriage return. It's always a good idea to include a few extra equal signs at the end of your group to ensure that AMAX fully exits when the commands are executed. NOTE: The file request module works slightly different when the -g option is used, in that if file requests are pending for a system, it will not prompt whether you want the pending requests displayed. With this in mind, you can plan a -g command grouping to assume that no requests are pending, even if they are. Here are some sample command groupings for some common functions: FILE REQUESTS Format: -gR<address>=<filename>=<password>==== Sample Without Password: -gR104/36=FOOBAR.ARC===== Sample With Password: -gR132/101=FILES=MYPASS==== SEND A FILE Format: -gS<address>=<filename>=<flavor>NN=== Sample With CONTINUOUS Flavor (Letter "C"): -gS104/36=C:\FILE\FOOBAR.ARC=CNN=== Sample With HOLD Flavor (Letter "H"): -gS132/101=C:\FILE\MYFILE.ZIP=HNN=== Note: Use "C" for Continuous, "D" for Direct, "N" for Normal, and "H" for Hold. POLL A NODE Format: -gP<address>=Y=== Sample: -gP104/36=Y=== LIST SEND OF A FILE USING PLEASE.ALL Format: -gL==<keyword>=F<filename>=<flavor>=== Sample With CONTINUOUS Flavor, Keyword TEST: -gL==TEST=FC:\FILE\FOOBAR.ARC=C=== Sample With HOLD Flavor, Keyword STUFF: -gL==STUFF=FD:\BBS\LOGFILE.ARC=H=== AMAX Version 2.20 - Documentation - Page 25 -i This option is valid only if you use more than one 'Address' statement in your configuration file. If used, it tells AMAX to bypass the address selection section on start-up, and to use the primary (first appearing) address. -m The -m option tells AMAX to generate a courtesy message packet in "Normal" flavor for each file request entered. This will allows the receiving Sysop to know that a file request has been made, and is generally regarded as a courtesy. -n Tells AMAX to operate in "nodelistless" mode. AMAX will not look for a compiled nodelist and will not load a nodelist index file. This option can be used even if you have a nodelist available, and will save usage of memory equal to the size of your nodelist index. -p The -p option tells AMAX the name of a batch file that invokes your packer, used in conjunction with the Invoke Packer command on AMAX's Main Functions menu. This option could also name a program, but no parameters could be passed to the program. In other words, NO COMMAND LINE ARGUMENTS CAN BE DESIGNATED. Call a batch file, and have the batch file pass any parameters to the packing program itself. -s The -s option allows you to set the default View/Edit Outbound function's sort mode. When a default is not set, you will be asked for a choice each time you use the View/Edit Outbound function. When using this option, "A" will cause an address sort, "T" will cause a type sort, and "F" will cause a flavor sort. "N" can also be used meaning no sort, and the information will be displayed as it is found in the outbound directory. All other letters are ignored. Note that the letters are NOT case sensitive. Examples: amax -d -sA amax -sF -t The -t option tells AMAX to suppress the use of a tearline and origin line when storing messages. When this option is NOT used, AMAX will by default add an origin line and a tearline of "--- AMAX 2.20" to the end of any messages saved AMAX Version 2.20 - Documentation - Page 26 with the Message Enter function. -u This option tells AMAX which unpacker to use for unpacking .ARC compatible compressed mail (ARCmail). "0" is the default, and designates ARCE (do not use -u at all if you use ARCE). "1" designates PKXARC, "2" designates PKUNPAK, and "3" designates PAK. ARC is not supported at this time. Example: amax -u1 amax -u3 TROUBLESHOOTING This section contains information that may be helpful if you encounter problems with AMAX. If you are unable to solve your problem, I am interested in hearing about it. My address is shown at the end of this documentation. PLEASE REFER TO SUPPORT.DOC INCLUDED WITH THE DISTRIBUTION PACKAGE FOR SUPPORT INFORMATION. Multi-Tasking Systems... Please note that when your outbound area is "active" (the system is involved in a NetMail session) some unexpected results can occur when checking the area. File attach contents can appear garbled, for example (due to flags and so on that your software may use to keep track of things). In testing, no damage has occurred, but be aware that strange things may appear to be happening in some cases like this. You should avoid using AMAX while the system is running in a multi-tasking environment whenever possible. AMAX does NOT feature file locking compatibility. Compressed Mail Addresses Incorrect... This situation may occur when an installation changes FidoNet addresses, or when a point converts to a regular node. The naming scheme for compressed mail is dependent on the address of the sending system (yours). AMAX uses your PRIMARY address (if more than one) as given in the configuration file to determine the destination address of compressed mail. Therefore, when you change your address, the destination shown for compressed mail when using View/Edit Outbound will be improperly calculated and displayed. Delete all such compressed mail packets (if they are sent and are zero-length) if your address change is permanent. Remote Use and Bizarre Cursor Positioning... In beta testing, problems have been reported when AMAX is used remotely with some communications programs. AMAX uses AMAX Version 2.20 - Documentation - Page 27 ANSI X3.64 compatible screen control codes, equivalent to the DOS 3.x ANSI.SYS driver. Apparently when a communications program does not fully support the ANSI X3.64 standard, some control codes may not be interpreted as expected. Terminal programs with status bars are not recommended. AMAX's remote use capability was tested in development with BinkleyTerm's Terminal Mode under DOS 3.3. Garbled Screen on Local Use... When direct screen writes are not employed, AMAX uses ANSI control codes for cursor positioning. When DOS' ANSI.SYS driver is not installed, AMAX will appear to display streaming garbage. Make certain that ANSI.SYS is being installed at boot-time via your CONFIG.SYS file. Refer to your DOS manual for details. You may also wish to simply enable direct screen writes, which do not require ANSI.SYS. Garbled Screen on Remote Use... AMAX uses ANSI screen control codes for cursor positioning. If garbage is being displayed, your remote terminal doesn't support ANSI control codes. Properly configure or change your communications program. Spurious and Garbled Entries in Outbound Area... AMAX uses an intelligent routine to figure out what all is in your outbound area, but if "foreign" files exist in the outbound area, they may be misinterpreted by AMAX, and subsequently displayed as or with garbage on the screen. As is stated numerous times in both the BinkleyTerm documentation, the outbound mail holding area is to be used ONLY for legitimate mail files. DO NOT place other types of files in the area. AMAX does know about all the various files that may legitimately be found in the outbound area. SOLVING SPECIFIC OUTBOUND MAIL PROBLEMS This section gives some common problems with outbound mail, and offers some solutions possible by using AMAX. If you are having problems not addressed here, I'd like to know; my address is shown elsewhere in the documentation. I will consider adding a feature or documentation section if necessary. Stray Packets in Outbound Area... Stray packets are caused by packer software failure. This often occurs in limited memory situations, such as multi- tasking. When packing compressed mail, the packer, normally oMMM, changes packet names to the normal FidoNet convention AMAX Version 2.20 - Documentation - Page 28 (with .PKT extension) for archiving into compressed mail. When there is not enough memory to load the archiving utility (ARCA, PKPAK, PKARC, ZOO, ZIP or LHARC), oMMM (or whatever packer you use) fails to create compressed mail, but leaves the packets that were to be archived in the outbound area. You can use AMAX PacketView (select "More" for the stray packet under View/Edit Outbound) to examine the packet and determine it's proper destination address. Write down the proper destination address of the stray packet. At the View/Edit Outbound menu, simply select the R)eroute function, and choose the desired stray packet. When you reroute a stray packet, it will be saved as a Normal packet addressed to the system you specify. Need to Add a File to Existing Attach... Use the Send a File function to send the desired file to the desired destination. Need to Delete a File from Existing Attach... Use the View/Edit Outbound function. Find the desired attach file. Select More which will list the files within the attach. Select "D" to delete a file reference. Choose the line number of the file reference to delete. NOTE! The original file itself (as referenced by the file attach) will NOT be changed or affected in any way when the reference is deleted. If the file was to be deleted or truncated after sending, that operation will need to take place manually! Need to Add a Message to an Existing Packet... Use the Message Entry function to type a message to the destination. Alternately, use your regular message editor to enter a message, and run your packer. The message will be appended to the existing packet. Need to Change or Delete a Message Within a Packet... Using the View/Edit Outbound function and the More option, determine the filename of the packet in question. You may wish to exit AMAX at this point to allow more memory to used by other programs during this process. Changing directory if needed, rename the packet to "12345678.PKT" and move the file (copy, then delete original) to your inbound files area. Change directory back to the original if needed. Invoke your unpacking software. AMAX Version 2.20 - Documentation - Page 29 The messages in the packet should then be tossed into your NetMail message area. Using your regular message editor or another utility, delete or change the message(s) as desired. Note that the messages from the packet should be marked "In Transit." Re-invoke your mail packer. Using the AMAX View/Edit Outbound function, find the packet (or packets) in question. Using PacketView, check to see that only the messages desired remain in the packet. Repeat the process if necessary. Need to Delete a Message from an Existing Compressed Mail Packet... Make sure that you have specified that compressed mail will be displayed. Choose the proper option from the appropriate menu if needed to enable this option. View/Edit Outbound, and find the compressed mail packet in question. Select More for the packet. Choose to have the compressed mail unpacked into a Normal flavor packet. Make sure that you have the unpacking software properly installed as specified earlier (see "General Use Information," "Compressed Mail Unpacking" sub-heading). Using the View/Edit Outbound function, find the newly created Normal packets for the destination system. Using PacketView, make certain that this packet contains the message(s) you want to delete. Follow the instructions from the previous section, "Need to Delete a Message from an Existing Packet..." When completed, your packer should have re-packed the messages into compressed mail. SUMMARY That about takes care of explaining the functionality of AMAX. Hopefully, you'll find AMAX to be handy, easy-to-use, and worth keeping around. AMAX will continue to evolve over time. Your input is valuable; user input and comments have made this version of AMAX what it is. If you have suggestions, please send them along to the author, but do so only if you have honored the license agreement. No promises are made about implementing any suggestions, but they will be duly considered, particularly if several requests for the same types of features are received. When making suggestions or comments, please keep in mind that the overall design consideration for AMAX is ease of use, intelligent functionality, and more importantly, something I call "program AMAX Version 2.20 - Documentation - Page 30 size efficiency." This means giving a lot of "bang" for the amount of disk real estate required to house the program. Although AMAX has over the years grown much larger than I wanted it to, I think for a program of its size, AMAX does a heck of a lot. I hope you feel the same way. Enjoy AMAX!